home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group00b.txt
/
000008_icon-group-sender _Fri Jul 7 08:45:23 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2001-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id IAA12521
for icon-group-addresses; Fri, 7 Jul 2000 08:45:08 -0700 (MST)
Message-Id: <200007071545.IAA12521@baskerville.CS.Arizona.EDU>
From: Atle <trollet@skynet.be>
X-Newsgroups: comp.lang.icon
Subject: Re: Error messages
Date: Fri, 07 Jul 2000 11:12:29 -0100
X-Trace: news0.skynet.be 962960788 28207 194.78.239.13 (7 Jul 2000 09:06:28 GMT)
X-Complaints-To: abuse@skynet.be
X-Accept-Language: en
To: icon-group@optima.CS.Arizona.EDU
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 690
> For something that is so line-oriented as assembler language is, I'd think that either Icon or
>SNOBOL/SPITBOL would be relatively ideal tools for writing your assembler. Although you COULD
>probably write it in Prolog, I have to wonder if the benefits of making that choice are enough to
>justify the hassle.
Well, it wasn't really the low-level routines for IO or code generation I though about, but the part where the assembler/compiler
decides what to do - and that is something ProLog should be good at - ant 'decide what to do' in most cases is either
pass it on
stop with error message
so deciding what err message to put out, should be be a ProLog problem, right?
Atle